<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>

<head>
    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
    <title>TestFire</title>


    <link rel=stylesheet href="../css/basic.css" type="text/css">
    <script type="text/javascript" src="http://localhost:8080/testFireServer/javascript/displayTools.js"></script>
</head>
<body>
<div id="masthead">
    <h1 id="siteName">TestFire</h1>

    <div id="globalNav">
        <a id="href_home" href="../index.html">Home</a> |
        <a id="href_download" href="../download/download.html">Download</a> |
        <a id="href_docs" href="index.html">Docs</a> |
        <a class="active" id="href_status" href="status.html">Status</a> |
        <a id="href_about" href="../about.html">About</a> |
    </div>

</div>
<!-- end masthead -->
<h2 id="pageName">Status Updates: </h2>

<div id="content">

    <div class="content_div">
        <h3>April 15, 2008</h3>

        <div class="status_update">
            <h2>Agent, Extension, Model</h2>

            <div class="txt">
                Goodness. It's been a while. Updated everything.
                <ol>
                    <li>
                        Load and Save! Under the TestFire drop-down.
                    </li>
                    <li>
                        Move Up/Move Down for everything that needs it - Actions, Action Groups, Tests (why not).
                    </li>
                    <li>
                        Action Groups now surround actions which require multiple steps. For instance, anything acting
                        on a component nested in multiple frames will require an action to aquire each frame, and an
                        action to perform the action (*sigh*, as in Set or AssertExists, see disambiguation, below).
                    </li>
                    <li>
                        Many usability fixes/improvements, error checking etc.
                    </li>
                </ol>
            </div>
             <div class="txt">
                 Disambiguation of 'Action': I made the mistake of calling the 'list of things to do', which contains
                 Assertions, Actions and BrowserCommands, 'Actions'. I will be changing this to 'Tasks' shortly, but
                 it is a fairly significant refactor. It WILL break your tests.
             </div>

        </div>

        <h3>Oct 16, 2007</h3>

        <div class="status_update">
            <h2>Agent, Extension</h2>

            <div class="txt">
                Continuing the major change of 'how things work', I've:
                <ol>
                    <li>
                        Added the TestsetManger page for the agent, which by default resides at <br>
                        <a href="http://localhost:9292/testsetManager.jsp">http://localhost:9292/testsetManager.jsp</a><br>
                        This allows for deleting and running testsets, at the moment. Create them in the Extension, of course.
                    </li>
                    <li>
                        Speaking of creating Testsets in the Extension, you can create a testset and push it to the
                        agent via the new Agent tab. Use 'save'.
                    </li>
                    <li>
                        Added a few hacks (*sigh*) to deal with how WATIJ fails to find frames using the <i>index</i> finder.
                        I'm not certain if this failure is documented and 'not-a-bug', or if there is some real problem there.
                        Either way, frames are properly handled now, *no matter how deep*. Bwaahahah. (cough).
                    </li>
                    <li>
                        The agent now stores saved tests in xml format. Results are appended onto the saved testset
                        on each run. Combine this with the ugly super-basic management page and I can see this being
                        a real pain in short order. I intend to create an ExtJS based page for this, again, when I can
                        get to it.
                    </li>
                </ol>
                The management server is still broken. I am going to keep it broken until I've cleared up a lot of the
                bugs in the local-only mode.
            </div>

        </div>
        <h3>Oct 02, 2007</h3>

        <div class="status_update">
            <h2>All</h2>

            <div class="txt">
                In a major change of 'how things work', I've:  
                <ol>
                    <li>
                        Removed the use of the custom Http Server, and implemented embedded Tomcat for server all
                        requests. We will still need the HttpClient package for Agent-Pull against the management
                        server.
                    </li>
                    <li>
                        Implemented the ability to send testsets directly from the Extension to the local Agent, to be
                        saved, and to be run immediatly.
                    </li>
                </ol>
                This has broken most of the functionality of the management server for the moment. Since the source is
                not yet ready to be released, this isn't a HUGE deal. I hope to actually finish the licensing tonight,
                and upload it to the gettestfire.org site.
            </div>
            <div>
                Also, I've not implemented storage on the local server yet. Apologies. You can still PUSH a testset
                onto the management server, which will save them.
            </div>
        </div>
   
    <h3>Sept 26, 2007</h3>

    <div class="status_update">
        <h2>All</h2>

        <div class="txt">
            The project as a whole is approximatly stable enough to use: 'alpha state' if you will.
            It is just far from feature complete.
            When taken as a framework, it is very far along. When taken as a completed application suite, it
            is sadly lacking.
        </div>
        <div class="txt">
            The source will be released shortly, however due to the size of the project and the number of
            libraries, how it is organized etc, it is going to take a while to organize the licensing.
        </div>
        <div class="txt">
            The Extension, or at least the parts that require it, will utilize the same license as Firebug,
            in spite of the fact that I absolutly despise the Mozilla Public License (MPL).
            Maybe I hate it because it has the word 'Netscape' in it. But it's
            probably because section 6.2 makes it completely unpredicatble and generally worthless. I digress.
        </div>
        <div class="txt">
            The remainder of code will be licensed under the MIT license wherever possible.
        </div>
        <div class="txt">
            The remainder of code will be licensed under the MIT license wherever possible.
        </div>


        <div class="txt todo_item">
            <h4>Todo:</h4>
            <ol>
                <li>
                    Validate and apply licensing text. The body of the code won't actually be shockingly hard
                    to valididate. However, the number of support jars and libraries is very significant and
                    must be taken into account: we can't just include it in the SVN checkout, but to
                    manually aquire each resource and place it in the location the build system expects to
                    find it in... will be a very painful experience for each developer.
                </li>
                <li>
                    Find a host. If we decide to use Sourceforge, all it will be is svn hosting. Google
                    code has an issue tracker that wouldn't kill me to use (I despise the sourceforge site, sorry).

                </li>
            </ol>
        </div>
    </div>

    <div class="status_update">
        <h2>Support</h2>

        <div class="txt">
            Created the public www.testfire.com website (what you are looking at). No error reporting form
            yet, sorry (printing an e-mail address on a public web site is inbox-suicide, sorry).
        </div>


        <div class="txt todo_item">
            <h4>Todo:</h4>
            <ol>
                <li>
                    Need to look into Jira for managing the open issues and bugs. IIRC they offer a free version for
                    open source projects.
                </li>
                <li>

                </li>
            </ol>
        </div>
    </div>
    <div class="status_update">
        <h2>TestFireExtension</h2>

        <div class="txt">
            The extension is ready for... let's call it alpha release. Most of the more important bits work, the
            engine is in place, and it is ready for the help of other devs. But there are a whole slew of known
            issues.
        </div>
    </div>


</div>


</div>

<script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
</script>
<script type="text/javascript">
_uacct = "UA-2723004-1";
urchinTracker();
</script>
</body>
</html>

